chore(deps): bump golang.org/x/crypto to v0.52.0#605
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
osm6495
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remediates the open CRITICAL Dependabot alert for
golang.org/x/cryptoby bumping it fromv0.45.0tov0.52.0(patched version).golang.org/x/crypto v0.52.0requires Go >= 1.25, so this also bumps the modulegodirective1.24.0 → 1.25.0(and drops the now-redundanttoolchain go1.24.1line). CI resolves its Go version fromgo.mod(go-version-file: go.mod); there are no Dockerfile pinned Go versions to update.Transitive
golang.org/x/{net,sys,text,term}were pulled forward bygo mod tidyas a consequence. Thevendor/tree was regenerated viago mod vendor— hence the large (mechanical) vendored diff.CI lint compatibility (
ci:commit)The Go 1.25 bump broke the CI
go-testsjob: the pinnedgolangci-lint v1.64.4(built with Go 1.24) refuses to target ago 1.25.0module. Upgraded the lint step togolangci-lint-action@v8.0.0+golangci-lint v2.5.0(built with Go 1.25) and migrated.golangci.ymlto the v2 schema (viagolangci-lint migrate).To preserve the prior effective linter behavior (and avoid reformatting unrelated source), the v2-only linters that would otherwise fire on existing code are disabled (
funcorder,godoclint,noinlineerr,wsl_v5), and staticcheck is configured to exclude theST1*/QF1*check groups (v1 hadstylecheckdisabled). The oldgoimportslocal-prefixessetting was dropped because the v1 config used the misspelled keylinter-settings, so it was silently ignored and never enforced.Verified locally:
go build ./...,go vet ./...,go test ./..., andgolangci-lint run ./...(v2.5.0) all pass. CI green.Link to Devin session: https://app.devin.ai/sessions/77c5bbaf5b114aac80ad2c021c2b14f4
Requested by: @kparkinson-ld